Centralized Service for Awakening a Computing Device

ABSTRACT

Various technologies and techniques are disclosed for providing and interacting with a centralized wake service. A server-side wake service is provided that is operable to allow applications to subscribe to the wake service. The wake service receives a wake request directed to a particular computing device from a particular one of the applications. The wake request is forwarded from the wake service to a client-side communication service on the particular computing device if forwarding is determined to be appropriate. When the client-side communication service on the particular computing device receives the wake request while in a reduced power mode, the computing device wakes up and an appropriate response is determined.

This application is a continuation application of co-pending U.S. patentapplication Ser. No. 11/710,708 filed in the U.S. Patent and TrademarkOffice on Feb. 26, 2007.

BACKGROUND

Computing devices of today have various power mode settings that controlwhen various subsets of the device turn off to conserve power. Laptopstypically find these power mode settings to be most helpful, so batterylife can be preserved when the computing device is not in use.

More and more services are being designed to follow the user around andcommunicate with the user wherever they may be. Email, instantmessaging, voice-over-IP and other such network services are just a fewexamples of such services. However, today's world of “always-on” and“always-available” comes into direct conflict with the idea of a reducedpower mode that is available on most computing devices. In other words,once the computer enters the reduced power mode, many network servicescan no longer communicate with the user to achieve the desired goal.

SUMMARY

Various technologies and techniques are disclosed for providing andinteracting with a centralized wake service. A server-side wake serviceis provided that is operable to allow applications to subscribe to thewake service. The wake service receives a wake request directed to aparticular computing device from a particular one of the applications.The wake request is forwarded from the wake service to a client-sidecommunication service on the particular computing device if forwardingis determined to be appropriate. In one implementation, varioussettings, such as power information, user contact preferences, and userpresence information that were provided by the client-side communicationservice are used to determine whether forwarding is appropriate.

When the client-side communication service on the particular computingdevice receives the wake request while in a reduced power mode, thecomputing device wakes up and an appropriate response is determined. Inone implementation, an appropriate response includes responding to thewake service to acknowledge the request, and then pursuit ofcommunications with the particular application that requested the wake.

This Summary was provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic view of a computer system using a centralizedwake service of one implementation.

FIG. 2 is a diagram of one implementation that illustrates how some ofthe physical components of the computer system of FIG. 1 correlate toparticular logical components.

FIG. 3 is a diagrammatic view of client-side communication applicationof one implementation operating on the computer system of FIG. 1.

FIG. 4 is a diagrammatic view of server-side wake application of oneimplementation operating on the computer system of FIG. 1.

FIG. 5 is a high-level process flow diagram for one implementation ofthe system of FIG. 1.

FIG. 6 is a process flow diagram for one implementation of the system ofFIG. 1 illustrating the stages involved in providing a client-sidecommunication service.

FIG. 7 is a process flow diagram for one implementation of the system ofFIG. 1 illustrating the stages involved in providing a server-side wakeservice.

FIG. 8 is a diagrammatic view of a computer system of oneimplementation.

DETAILED DESCRIPTION

For the purposes of promoting an understanding of the principles of theinvention, reference will now be made to the embodiments illustrated inthe drawings and specific language will be used to describe the same. Itwill nevertheless be understood that no limitation of the scope isthereby intended. Any alterations and further modifications in thedescribed embodiments, and any further applications of the principles asdescribed herein are contemplated as would normally occur to one skilledin the art.

The system may be described in the general context as an applicationthat wakes computing devices from reduced power modes, but the systemalso serves other purposes in addition to these. In one implementation,one or more of the techniques described herein can be implemented asfeatures within a server-side wake service, a client-side communicationservice, and/or from any other type of program or service that managescommunications between applications over a network.

In one implementation, a centralized wake service is provided thatallows computing devices to be awakened when they are in a reduced powermode by network applications. For example, a voice-over-IP communicationapplication may contact the wake service when it wishes to communicatewith a particular computing device. The wake service uses informationabout the particular computing device to communicate with that computingdevice and to wake it from the reduced power mode if the particularcomputing device is in the reduced power mode so the communications cancontinue. In one implementation, various settings, such as one or morepolicies, allow the particular device to indicate when it should beawakened and when it should not be awakened.

FIG. 1 is a diagrammatic view of a computer system 10 using such acentralized wake service 14 of one implementation. One or more wakeservers 12 host the centralized wake service 14. The term “server” asused herein is meant to broadly include computer servers, routers,and/or other components present in a network infrastructure that couldprovide a service to other computers and/or components on a network.Various network applications 16, such as email, voice-over-IP, instantmessaging, and so on are able to communicate with the wake service 14over a network 18, such as the Internet. One or more computing devices20 are able to communicate with the wake service 14 over the network 18.When one of the network services 16 wishes to communicate with computingdevice 20 even when it is in a reduced power mode, the particularnetwork service 16 can contact the wake service 14 for assistance.

Turning now to FIG. 2, a diagram of one implementation illustrates howsome of the physical components of the computer system of FIG. 1correlate to particular logical components. For example, the networkapplications 16 communicate with application programming interfaces forinternet services 50 in order to utilize the wake service 14 of wakeserver 12. The particular computing device 20 communicates withapplication programming interfaces for and/or to computing devices, suchas the client-side communication application 200 as described in FIG. 3.In one implementation, the core logic 52 and wake-up packet mechanism 56are contained in the server-side wake service 14, such as theserver-side wake application 230 described in FIG. 4. The wake-up packetmechanism 56 communicates with the particular computing device 20 towake it from a reduced power mode when desired.

Turning now to FIG. 3, client-side communication application 200operating on computing device 600 (of FIG. 8) is illustrated. In oneimplementation, client-side communication application 200 is one of theapplication programs that reside on computing device 600 (of FIG. 8).However, it will be understood that client-side communicationapplication 200 can alternatively or additionally be embodied ascomputer-executable instructions on one or more computers and/or indifferent variations than shown on FIG. 8. Alternatively oradditionally, one or more parts of client-side communication application200 can be part of system memory 604 (on FIG. 8), on other computersand/or applications 615 (on FIG. 8), or other such variations as wouldoccur to one in the computer software art.

Client-side communication application 200 includes program logic 204,which is responsible for carrying out some or all of the techniquesdescribed herein. Program logic 204 includes logic for providing aclient-side communication service that is operable to run on a computingdevice on a software or hardware component and to communicate with awake service on a server, the wake service being responsible formanaging connectivity requests from a plurality of applications 206;logic for receiving a wake request from the wake service, even while thecomputing device is in a reduced power mode (which may be located inhardware, firmware, and/or software, etc.) 208; logic for waking up thecomputing device from the reduced power mode upon receiving the wakerequest, if applicable 210; logic for determining an appropriateresponse to the wake server (such as by analyzing one or more policies)212; logic for sending communication details to the wake service, suchas user contact preferences, availability, security settings, policysettings, and current state 214; and other logic for operating theapplication 220. In one implementation, program logic 204 is operable tobe called programmatically from another program, such as using a singlecall to a procedure in program logic 204.

Turning now to FIG. 4, server-side wake application 230 operating oncomputing device 600 (of FIG. 8) is illustrated. In one implementation,client-side communication application 200 is one of the applicationprograms that reside on computing device 600 (of FIG. 8). However, itwill be understood that server-side wake application 230 canalternatively or additionally be embodied as computer-executableinstructions on one or more computers and/or in different variationsthan shown on FIG. 8. Alternatively or additionally, one or more partsof server-side wake application 230 can be part of system memory 604 (onFIG. 8), on other computers and/or applications 615 (on FIG. 8), orother such variations as would occur to one in the computer softwareart.

Server-side wake application 230 includes program logic 234, which isresponsible for carrying out some or all of the techniques describedherein. Program logic 234 includes logic for providing a server-sidewake service that is operable to allow a plurality of applications tosubscribe to the wake service over a network 236; logic for receiving awake request directed to a particular computing device from a particularone of the applications (e.g. because the particular application wishesto communicate with the particular computing device) 238; logic forforwarding the wake request to a client-side communication service onthe particular computing device if forwarding is determined to beappropriate 240; logic for communicating with the client-sidecommunication service on the particular computing device to obtain stateinformation about the particular computing device, such as powerinformation, system connectivity information, and administrativeconfiguration information 242; logic for communicating with theclient-side communication service prior to forwarding the wake requestto determine if forwarding is appropriate 244; and other logic foroperating the application 250. In one implementation, program logic 234is operable to be called programmatically from another program, such asusing a single call to a procedure in program logic 234.

Turning now to FIGS. 5-7 with continued reference to FIGS. 1-2, thestages for implementing one or more implementations of client-sidecommunication application 200 and/or server-side wake application 230are described in further detail. FIG. 5 is a high level process flowdiagram for system 10. In one form, the process of FIG. 5 is at leastpartially implemented in the operating logic of computing device 600 (ofFIG. 8). The process begins at start point 270 with providing at leastone server operable to communicate with one or more client computingdevices over a network, the server having a wake service (stage 272). Atleast one application is provided with an ability to communicate withthe wake service over the network, the application being operable tosend a wake request to the wake service when the application desires tocommunicate with a particular one of the computing devices (stage 274).

The wake service is provided with the operability to communicate with aclient-side communication service on the particular computing device toobtain state information, such as to determine if forwarding of the wakerequest is appropriate (stage 276). The wake service is provided withthe operability to forward the wake request to the particular computingdevice if the wake service determines forwarding is appropriate based ona set of policies (stage 278). As a few non-limiting examples, the setof policies may help the wake service determine if it is appropriate towake up the computing device from a reduced power mode, if the computingdevice is not in reduced power mode and is ready for communications,etc.) (stage 278). The process ends at end point 280.

FIG. 6 illustrates one implementation of the stages involved inproviding a client-side communication service. In one form, the processof FIG. 6 is at least partially implemented in the operating logic ofcomputing device 600 (of FIG. 8). The process begins at start point 290with providing details from a computing device to a wake service on howto wake the computing device when it is in a reduced power mode (such asany time network connections change) (stage 292). As the computingdevice enters a reduced power mode, the client-side communicationapplication on the computing device notifies the wake service toindicate current connection details (stage 294). The wake service canmaintain a cache on the last known location for the computing deviceusing these connection details (stage 294). At a later point in time, awake request is received by the client-side communication applicationfrom the wake service (stage 296). The computing device is awakened fromthe reduced power mode and optionally communicates with a particularapplication that requested the wake through the wake service (stage298). The process ends at end point 300.

FIG. 7 illustrates one implementation of the stages involved inproviding a server-side wake service. In one form, the process of FIG. 7is at least partially implemented in the operating logic of computingdevice 600 (of FIG. 8). The process begins at start point 310 withreceiving a request from a network service (such as voice-over-IP,instant messaging, email, etc.) to send a wake request to a particularcomputing device (because they have been unable to communicate directlyand need assistance, etc.) (stage 312). The user presence information,power information, and user contact preferences are used to decidewhether or not to send a wake request to the particular computing devicefrom a wake service (stage 314). If a wake request is determined to beappropriate, then the server-side wake service sends the wake request tothe particular computing device (e.g. in a secure data packet) (stage316). If the wake request is successful, then the wake service willreceive a response from the particular computing device and will notifythe requesting network service that the wake request was successful socommunications can pursue (stage 318). If the wake request is notsuccessful, the wake service will notify the requesting network servicethat the wake request was not successful (stage 320). The process endsat end point 322.

As shown in FIG. 8, an exemplary computer system to use for implementingone or more parts of the system includes a computing device, such ascomputing device 600. In its most basic configuration, computing device600 typically includes at least one processing unit 602 and memory 604.Depending on the exact configuration and type of computing device,memory 604 may be volatile (such as RAM), non-volatile (such as ROM,flash memory, etc.) or some combination of the two. This most basicconfiguration is illustrated in FIG. 8 by dashed line 606.

Additionally, device 600 may also have additionalfeatures/functionality. For example, device 600 may also includeadditional storage (removable and/or non-removable) including, but notlimited to, magnetic or optical disks or tape. Such additional storageis illustrated in FIG. 8 by removable storage 608 and non-removablestorage 610. Computer storage media includes volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Memory604, removable storage 608 and non-removable storage 610 are allexamples of computer storage media. Computer storage media includes, butis not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can accessed by device 600. Anysuch computer storage media may be part of device 600.

Computing device 600 includes one or more communication connections 614that allow computing device 600 to communicate with othercomputers/applications 615. Device 600 may also have input device(s) 612such as keyboard, mouse, pen, voice input device, touch input device,etc. Output device(s) 611 such as a display, speakers, printer, etc. mayalso be included. These devices are well known in the art and need notbe discussed at length here. In one implementation, computing device 600includes client-side communication application 200 (of FIG. 3). Inanother implementation, computing device includes server-side wakeapplication 230 (of FIG. 4).

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims. All equivalents, changes, andmodifications that come within the spirit of the implementations asdescribed herein and/or by the following claims are desired to beprotected.

For example, a person of ordinary skill in the computer software artwill recognize that the client and/or server arrangements, userinterface screen content, and/or data layouts as described in theexamples discussed herein could be organized differently on one or morecomputers to include fewer or additional options or features than asportrayed in the examples.

1. A computing device comprising: logic for providing a communicationservice to provide details regarding how to wake the computing devicewhen the computing device is operating in a reduced power mode; logicfor receiving a wake request when the computing device is operating inthe reduced power mode; logic for waking the computing device from thereduced power mode upon receiving the wake request; and logic fordetermining an appropriate response to the received wake request basedon analyzing one or more policies.
 2. The computing device of claim 1,further comprising: logic for sending a notification indicating currentconnection details as the computing device enters the reduced powermode.
 3. The computing device of claim 1, further comprising: logic forsending the appropriate response, after successfully waking from thereduced power mode in response to receiving the wake request anddetermining the appropriate response.
 4. The computing device of claim1, wherein the details regarding how to wake the computing device whenthe computing device is in a reduced power mode include at least one ofuser contact preferences, availability information, security settings,policy settings, or current state information.
 5. The computing deviceof claim 1, wherein the computing device further comprises logic forproviding state information in response to receiving a communication forobtaining the state information.
 6. The computing device of claim 5,wherein the state information includes power settings.
 7. The computingdevice of claim 5, wherein the state information includes useradministrative configuration information.
 8. The computing device ofclaim 5, wherein the state information includes system connectivityinformation.
 9. A computing device comprising: means for providingdetails regarding how to wake the computing device when the computingdevice is operating in a reduced power mode, the details including oneor more policies indicating when the computing device is to be awakenedand when the computing device is not to be awakened; means for receivinga wake request and waking the computing device when the computing deviceis operating in the reduced power mode; and means for determining anappropriate response to the received wake request based on analyzing theone or more policies.
 10. The computing device of claim 9, furthercomprising: means for sending a notification indicating currentconnection details as the computing device enters the reduced powermode.
 11. The computing device of claim 9, further comprising: means forsending the appropriate response, after successfully waking from thereduced power mode in response to receiving the wake request.
 12. Thecomputing device of claim 9, wherein the details regarding how to wakethe computing device when the computing device is operating in thereduced power mode include user contact preferences.
 13. The computingdevice of claim 9, wherein the details regarding how to wake thecomputing device when the computing device is operating in the reducedpower mode include availability information.
 14. The computing device ofclaim 9, wherein the details regarding how to wake the computing devicewhen the computing device is operating in the reduced power mode includeavailability information.
 15. The computing device of claim 9, whereinthe details regarding how to wake the computing device when thecomputing device is operating in the reduced power mode include currentstate information.
 16. The computing device of claim 15, wherein thecurrent state information includes user administrative configurationinformation.
 17. The computing device of claim 15, wherein the currentstate information includes system connectivity information.